Skip Headers

Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# Performing User-Managed TSPITR of Partitioned Tables When a Partition Has Split

This section describes how to recover partitioned tables when a partition has been split, and includes the following sections:

- Step 1: Drop the Lower of the Two Partitions at the Primary Database

- Steps 2: Follow Same Procedure as for Partial TSPITR of Partitioned Tablespaces

## Step 1: Drop the Lower of the Two Partitions at the Primary Database

For each partition you wish to recover whose range has been split, drop the lower of the two partitions so that the higher expands downwards. In other words, the higher partition has the same range as before the split. For example, if `P1` was split into partitions `P1A` and `P1B`, then `P1B` must be dropped, meaning that partition `P1A` now has the same range as `P1`.

For each partition that you wish to recover whose range has split, create a table that has exactly the same column names and column datatypes as the partitioned table you are recovering. For example, execute the following, replacing the variables with the appropriate values:

    CREATE TABLE new_table
    AS
    (
      SELECT *
      FROM partitioned_table
      WHERE 1=2
    );

These tables will be used to exchange each recovery set partition in "Step 3: Exchange Partitions with Standalone Tables".

## Steps 2: Follow Same Procedure as for Partial TSPITR of Partitioned Tablespaces

Follow the same procedure as for "Performing Partial TSPITR of Partitioned Tables", but skip the first step of this procedure: "Step 1: Create a Table on the Primary Database for Each Partition Being Recovered". In other words, start with "Step 2: Drop the Indexes on the Partition Being Recovered" and follow all subsequent steps.